Changes between Version 9 and Version 10 of Scripting and Plugins

Timestamp:

Jan 25, 2008, 3:22:12 PM (16 years ago)

Author:

indrora

Comment:

--

Scripting and Plugins

@@ -22 +22 @@
  * Some plugins that ship with Pidgin, Finch, and libpurple don't compile by default.  To compile these plugins, change to the appropriate directory in the source tree.  The directories you have to choose from are `pidgin/plugins`, `libpurple/plugins`, and `finch/plugins`.  Once in that directory, run the command `make filename.so`, where filename is the name of the plugin.  For example, the Offline Messaging plugin is called offlinemsg.c, so if you wanted to build that plugin, you would run `make offlinemsg.so`.  To install and use the plugin, you can copy the .so file to `~/.purple/plugins` (creating the directory if needed) or to `$PREFIX/lib/purple-2` for libpurple plugins, `$PREFIX/lib/pidgin/` for Pidgin plugins, or `$PREFIX/lib/finch` for Finch plugins.
  * Some third-party plugins rely on our build infrastructure, and will compile using the same instructions as our non-default plugins.  Plugin authors should provide this information, if applicable to their plugin(s), on their site.
- * For plugins that are not in the main build tree for Pidgin/libpurple (such as pidgin-rhythmbox), you must install the development files for Pidgin/libpurple development files. On Debian systems (such as ubuntu), this can be achieved with '''{{{ # apt-get install pidgin-dev }}}''' Followed by the normal configure/make procedure
+ * For plugins that are not in the main build tree for Pidgin/libpurple (such as pidgin-rhythmbox), you must install the development files for Pidgin/libpurple. On Debian systems (such as ubuntu), this can be achieved with '''{{{ # apt-get install pidgin-dev }}}''' Followed by the normal configure/make procedure
 
 == How do I compile a plugin? (Windows) ==